Skip to content

Use hardware channel activity detection for checking interference#8

Open
weebl2000 wants to merge 5 commits intodevfrom
use-hardware-channel-activity-detection
Open

Use hardware channel activity detection for checking interference#8
weebl2000 wants to merge 5 commits intodevfrom
use-hardware-channel-activity-detection

Conversation

@weebl2000
Copy link
Owner

Using RSSI isn't very reliable (it's disabled in the code for a reason). We might try hw channel activity detection. Since we are gonna TX anyway it shouldn't be too bad to listen for a few milliseconds first. Worst case we see there is a transmission and we wait a little while. Alternative is that we just TX anyway and intefere with others causing transmission collisions.

Would be great if people could test this on their repeaters & companions and see if TX becomes more reliable.

You can build firmware for you device using https://mcimages.weebl.me?commitId=use-hardware-channel-activity-detection

First impressions after flashing this on one of my repeaters that is high up & exposed to a lot of other repeaters is that it responds a little more consistently. Sometimes it's snappier, but often times it's slightly slower but it fails way less. I.e. less failed status requests & non-answered commands.


Mirror of meshcore-dev#1727

@weebl2000 weebl2000 force-pushed the use-hardware-channel-activity-detection branch from bc39bcc to 75da5d5 Compare February 28, 2026 18:13
@weebl2000 weebl2000 force-pushed the use-hardware-channel-activity-detection branch from 75da5d5 to 8bd55b6 Compare March 3, 2026 14:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants